Deploy StatusCake SSL Checks for public endpoints #182
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DrizzlyOwl
force-pushed
the
tf-statuscake-tls-monitor
branch
from
0b298ef to
62cb775
Compare
DrizzlyOwl
force-pushed
the
tf-statuscake-tls-monitor
branch
from
62cb775 to
18b8090
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
Stretch96
approved these changes
Oct 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the change?
Deploy 3 SSL Checks and a Contact Group on StatusCake
Why do we need the change?
Azure Monitor is not very reliable for TLS validity checks so we're using StatusCake instead.
We can deploy a SSL Certificate validity check that polls the dev, test, and prod health check endpoints once every 24H and notify us via Slack (integration)/Email at 14, 7 and 3 days before expiry
What is the impact?
None